Flash is only sending one parameter to this page, so the variable
is set to the first parameter in the params array. Flash can also
pass named params - in which case this page could refer to them as;
FLASH.paramName
In this example;
FLASH.yourName
--->
<cfset yourName = flash.params[1]>
<!--- Do something with the information that came from Flash... --->
<cfset aGreeting = "Hello, " & yourName & "!">
<!--- And send it back in the FLASH.result variable --->
<cfset flash.result = aGreeting> <!---
**
* CFMX Example Applications
*
* Copyright (c) 2002 Macromedia. All Rights Reserved.
*
* YOUR RIGHTS WITH RESPECT TO THIS SOFTWARE IS GOVERNED BY THE
* TERMS AND CONDITIONS SET FORTH IN THE CORRESPONDING EULA.
*
**
--->
<cfmodule template="../tags/layout.cfm" pageName="Flash Example 2 - Hello To You">
<p>
The previous example had information (a simple greeting) passed from the server to the client. Nearly all applications, however, require information to pass both ways - from client to server and back. In this example, a user enters a string in the Flash application. Flash then passes that string to the server to be used in an action there.
* Copyright (c) 2002 Macromedia. All Rights Reserved.
*
* YOUR RIGHTS WITH RESPECT TO THIS SOFTWARE IS GOVERNED BY THE
* TERMS AND CONDITIONS SET FORTH IN THE CORRESPONDING EULA.
*
**
--->
<cfmodule template="../tags/bts_layout.cfm" exampleName="Flash Example 3 - News Ticker"
source="index.cfm,newsdata.cfm,flash3.cfc"
keyTags="">
<p>
The first two examples used CFML templates to provide server-side logic to the Flash application. In this and subsequent examples, ColdFusion Components (CFCs) are used. The page approach is somewhat limited in that it uses the special FLASH variable scope (FLASH.params, FLASH.result, etc.). This means that the page cannot be used for any other purpose. When logic is implemented in a CFC, however, it can power a Flash application as well as other consumers, such as cfml pages or web services, without the need to re-write any code. It also brings all of the other benefits of components (team collaboration, code reuse, etc.) to Flash/ColdFusion projects. To view the component's self-documenting page, <a href="flash3.cfc" target="_blank">click here</a>.
<br><br>
The Actionscript remains very similar when using CFCs over CFML pages. The major difference is that gatewayConnection.getService function points to the specific component instead of the directory (as was the case in the CFML page based examples) and the CFCs function is invoked instead of the CFML page. For example, a component <font face="Courier New">cfdocs\exampleapps\flash3\flash3.cfc</font> could be invoked as follows;<br><br>
<font face="Courier New">serverCall = gatewayConnection.getService("cfdocs.exampleapps.Flash3.Flash3", new getHeadlines());
</font>
</p>
</cfmodule><!---
**
* CFMX Example Applications
*
* Copyright (c) 2002 Macromedia. All Rights Reserved.
*
* YOUR RIGHTS WITH RESPECT TO THIS SOFTWARE IS GOVERNED BY THE
* TERMS AND CONDITIONS SET FORTH IN THE CORRESPONDING EULA.
*
**
Author:
S. Holmes / sholmes@breckcomm.com
Breckenridge Communications - www.breckcomm.com
3/6/2002
rcamden:
Updated getAllnews method to use xml newsfeed.
--->
<cfcomponent hint="This is the news object component which passes a query recordset to Flash.">
<!---
This is a simple component function which requires no input parameters,
and returns all the news currently found in the database.
--->
<cffunction name="getAllNews" access="remote" returnType="query" hint="This function returns the latest news from the db in a query object.">
